Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1576

reference: 357-tree-1
name: 1576
tree-preservation-order: undefined
357-tpo-1
uprn
address-text
point: POINT (-1.046972 50.892883)
geometry: MULTIPOLYGON (((-1.046873 50.892873,-1.046877 50.892892,-1.046891 50.892910,-1.046913 50.892924,-1.046941 50.892933,-1.046971 50.892936,-1.047002 50.892933,-1.047030 50.892925,-1.047052 50.892911,-1.047067 50.892894,-1.047072 50.892874,-1.047068 50.892855,-1.047054 50.892837,-1.047032 50.892823,-1.047004 50.892814,-1.046974 50.892810,-1.046943 50.892813,-1.046915 50.892822,-1.046893 50.892836,-1.046878 50.892853,-1.046873 50.892873)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL